feat(test): Add integration testing to solution#42
Merged
Conversation
… by test. test: Added bad credential client for various tests.
… testing due to object management in server.
Collaborator
Author
|
As of July 3, there are 4 integration tests that are failing, three due to #39 or one for unknown behavior expectation from Kepware API. I am going to track the API behavior more and potentially create a case for the product. Test results output will document these for visibility. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#35 - Added integration testing framework to validate SDK APIs against Kepware instances in local testing.
This will allow us to execute testing changes against actual instances of Kepware to ensure increased compatability validation with Kepware changes over time and future feature additions.